Space vehicle field unit and ground station system

ABSTRACT

A field unit and ground station may use commercial off-the-shelf (COTS) components and share a common architecture, where differences in functionality are governed by software. The field units and ground stations may be easy to deploy, relatively inexpensive, and be relatively easy to operate. A novel file system may be used where datagrams of a file may be stored across multiple drives and/or devices. The datagrams may be received out of order and reassembled at the receiving device.

CROSS REFERENCE TO RELATED APPLICATION

This application claims the benefit of U.S. provisional patentapplication No. 62/016,564 filed on Jun. 24, 2014. The subject matter ofthis earlier filed application is hereby incorporated by reference inits entirety.

STATEMENT OF FEDERAL RIGHTS

The United States government has rights in this invention pursuant toContract No. DE-AC52-06NA25396 between the United States Department ofEnergy and Los Alamos National Security, LLC for the operation of LosAlamos National Laboratory.

FIELD

The present invention generally relates to space vehicles, and moreparticularly, to a relatively low cost, highly reliable field unit andground station for a space vehicle that share common components.

BACKGROUND

In conventional field units and ground stations, different systemcomponents, designed by a variety of manufacturers, are integrated andused for the field unit and ground station. Also, different software isused for these systems. This adds cost and complexity while reducingreliability. Accordingly, a more cost-effective and reliable field unitand ground station system may be beneficial.

SUMMARY

Certain embodiments of the present invention may provide solutions tothe problems and needs in the art that have not yet been fullyidentified, appreciated, or solved by conventional field unit and groundstation systems. For example, some embodiments pertain to a field unitand ground station that use commercial off-the-shelf (COTS) componentsand share a common architecture, where differences in functionality aregoverned by software. In certain embodiments, a novel file system isused where frames of a file may be stored across multiple drives and/ordevices. The frames may be received out of order and reassembled at thereceiving device.

In an embodiment, an apparatus includes at least one hardware boardconfigured to enable operation of the apparatus as a field unit and aground station. Software controls whether the apparatus operates as afield unit or a ground station without physical modification to the atleast one hardware board.

In another embodiment, a field unit/ground station (FU/GS) box includesan analog radio board configured to send and receive radio signals viaan antenna. The FU/GS box also includes a digital radio board configuredto interface with the analog radio board and provide digital radiofunctionality. The FU/GS box further includes a microcontroller boardconfigured to provide processing for the FU/GS box and a backplane thatconnects the analog radio board, digital radio board, andmicrocontroller board, facilitating communication between the boards.Software controls whether the FU/GS box operates as a field unit or aground station without physical modification to the boards.

In yet another embodiment, a system includes at least one field unit andat least one ground station. The at least one field unit and the atleast one ground station have common hardware.

BRIEF DESCRIPTION OF THE DRAWINGS

In order that the advantages of certain embodiments of the inventionwill be readily understood, a more particular description of theinvention briefly described above will be rendered by reference tospecific embodiments that are illustrated in the appended drawings.While it should be understood that these drawings depict only typicalembodiments of the invention and are not therefore to be considered tobe limiting of its scope, the invention will be described and explainedwith additional specificity and detail through the use of theaccompanying drawings, in which:

FIG. 1 is a perspective view illustrating a deployed space vehiclesystem, according to an embodiment of the present invention.

FIGS. 2A and 2B are architectural diagrams illustrating a groundstation, according to an embodiment of the present invention.

FIG. 3 is a block diagram illustrating an RF box, according to anembodiment of the present invention.

FIG. 4 is a photograph illustrating a prototype RF box, according to anembodiment of the present invention.

FIG. 5 is a block diagram illustrating a lightning box, according to anembodiment of the present invention.

FIG. 6 is a photograph illustrating a prototype lightning box, accordingto an embodiment of the present invention.

FIG. 7 is a block diagram illustrating a ground station (GS) box,according to an embodiment of the present invention.

FIG. 8 is a photograph illustrating a prototype GS box, according to anembodiment of the present invention.

FIG. 9 is a photograph illustrating a prototype ground station antennaassembly, according to an embodiment of the present invention.

FIG. 10 is a perspective view illustrating the inside of a groundstation/field unit box, according to an embodiment of the presentinvention.

FIG. 11 is a perspective view illustrating a ground station/field unitbox, according to an embodiment of the present invention.

FIG. 12 is an architectural diagram illustrating a field unit system,according to an embodiment of the present invention.

FIG. 13 is a perspective view illustrating a field unit box, accordingto an embodiment of the present invention.

FIG. 14A is a photograph illustrating a closed field unit box, accordingto an embodiment of the present invention.

FIG. 14B is a photograph illustrating the field unit box with an opencase, according to an embodiment of the present invention.

FIG. 14C is a photograph illustrating stacked boards of the field unitbox, according to an embodiment of the present invention.

FIG. 15 is a screenshot illustrating ground station control software,according to an embodiment of the present invention.

FIG. 16 is a screenshot illustrating simplified ground station controlsoftware, according to an embodiment of the present invention.

FIG. 17 is a block diagram illustrating connection setup for a groundstation, space vehicle, and field unit system, according to anembodiment of the present invention.

DETAILED DESCRIPTION OF THE EMBODIMENTS

Some embodiments of the present invention pertain to a relatively lowcost field unit and ground station system that use the same boards andreuse the majority of the software. The field unit and ground stationmay use commercial off the shelf (COTS) components and have a relativelysimple software interface. The system may be highly reliable, operatingfor extended periods of time. The system may also be highly optimizedfor a wide variety of missions to improve performance and lower costs.In other words, the field unit and ground station may be readilyadaptable to a wide range of missions “out of the box,” and theprincipal hardware may be fully commoditized. The ground station may bea fully Internet-capable control station that can facilitateuser-defined, user-controlled custom space solutions. In certainembodiments, the user community may have full control of the system viasoftware, hardware, ease of use, and wide adoption.

FIG. 1 is a perspective view illustrating a deployed space vehiclesystem 100, according to an embodiment of the present invention. System100 includes a ground station 110, a space vehicle 120, and a field unit130. In some embodiments, there may be multiple ground stations,multiple field units, multiple space vehicles, or any combinationthereof. Furthermore, in some embodiments, space vehicles maycommunicate with one another and/or be individually customized toperform different missions or to have different capabilities in order tocreate a space vehicle “swarm” that has more capabilities than anyindividual space vehicle.

Ground station 110 provides command and control capabilities for spacevehicle 120 using two-way communication and for field unit 130 using thesatellite as a relay. Space vehicle 120 may collect data in accordancewith its mission and transmit the data to ground station 110. In someembodiments, field unit 130 collects data, space vehicle 120 collectsthe data from field unit 130, and space vehicle 120 relays the data toground station 110. In certain embodiments, ground station 110 transfersdata to space vehicle 120, and space vehicle 120 transfers the data tofield unit 130 at a later time. In some embodiments, ground station 110communicates with field unit 130 in real time or near-real time, usingspace vehicle 120 as a relay.

Ground Station and Field Unit

FIGS. 2A and 2B are architectural diagrams illustrating a ground station200, according to an embodiment of the present invention. An antenna 210is configured to facilitate two-way communication with space vehicles.Antenna 210 includes downlink antennas 212 and uplink antennas 214.Downlink antennas 212 and uplink antennas 214 each operate at afrequency of 915 megahertz (MHz) with a gain of 14 decibels-isotropic(dBi). Using two downlink antennas 212 and uplink antennas 214 enablescircular polarization. Combiners and custom brackets 216 fasten downlinkantennas 212 and uplink antennas 214 to antenna 210.

A rotor 220 moves antenna 210 to facilitate better reception. An RF box222 allows long cable runs and sends signals to and receives signalsfrom antenna 210. A mast 224 holds antenna 210, rotor 220, and RF box222 in an upright position. Transmitting (TX) and receiving (RX) cablesand rotor azimuth (AZ) and elevation (EL) cables run between, andconnect, rotor 220 and RF box 222.

A lightning box 230 is connected to RF box 222 via antenna TX and RXcables and rotor AZ and EL cables. Lightning box 230 is grounded andprotects other connected electronics from current surges due tolightning strikes. Lightning box 230 is also connected to a groundstation (GS) box 240 via antenna TX and RX cables and rotor AZ and ELcables. In some embodiments, these cables may be hundreds of feet longor more.

GS box 240 may be rugged, relatively easy to use, and be run from astandard personal computer, tablet computer, mobile phone, or any othersuitable computing device, such as laptop 250. Antenna 210, rotor 220,RF box 222, mast 224, lightning box 230, and GS box 240 may be compactand portable, allowing deployment in many locations. In certainembodiments, multiple computing systems may be used to control groundstation 200.

GS box 240, which is controlled by laptop 250, controls the orientationof antenna 210 via rotor control box 242 and sends data to/receives datafrom the space vehicle via transceiver box 244. GS box 240 also containssensitive electronics and cryptographic keys for communication. In someembodiments, GS box 240 may be attached to antenna 210 or integratedwith rotor 220 itself. In such embodiments, laptop 250, or any othersuitable computing device, may communicate remotely with GS box 240. Insuch embodiments, a user may potentially control the operation of groundstation 200 from any desired location. Laptop computer 250 communicateswith GS box 240 to send communication data to space vehicles, receivedigital space vehicle communication data, and control the orientation ofantenna 210 via rotor 220.

FIG. 3 is a block diagram illustrating an RF box 300, according to anembodiment of the present invention. RF box 300 includes a transmit andreceive chain to provide amplification in order to enable long cableruns between the ground station box and the antennas, and is placed nearthe antennas. RF box 300 may be powered by AC wall power to simplifysetup. The transmit chain includes a power amplifier (PA) 305, anisolator 310, a filter 315, and appropriate RF cable connectors(N-connectors 320), using an AC/DC power converter 325 to power PA 305.The receive chain includes a filter 330, a low noise amplifier (LNA)335, and appropriate RF cable connectors (N-connectors 340), using anAC/DC power converter 345 to power LNA 335.

FIG. 4 is a photograph illustrating a prototype RF box 400, according toan embodiment of the present invention. In RF box 400, the filters, LNA,and PA are visible. RF box 400 has a rugged, weatherproof, fullyenclosed outdoor case that houses the sensitive electronics inside.

FIG. 5 is a block diagram illustrating a lightning box 500, according toan embodiment of the present invention. Lightning box 500 providesprotection for the RF transmit and receive signal paths and the rotorcontrol signal paths. For RF protection, a standard RF lightningprotector may be used. For rotor control protection, separate AC and DCpaths may be provided to accommodate both types of signals usingstandard AC and DC lightning protection approaches.

FIG. 6 is a photograph illustrating a prototype lightning box 600,according to an embodiment of the present invention. Lightning box 600has a rugged case that houses internal electronics.

FIG. 7 is a block diagram illustrating a GS box 700, according to anembodiment of the present invention. GS box 700 houses the satelliteradio and antenna rotor controllers. The rotor controller may beaccessed by connecting GS box 700 to a computer using a USB cable. AUSB-to-RS-232 converter may be used to interface to the rotorcontroller. Custom bayonet/screw-on connectors may be provided on theoutside of GS box 700 to enable ground station setup without requiringtools. The controller may be powered by standard AC wall power. Thesatellite radio transceiver may be accessed by connecting GS box 700 toa computer using a USB cable, and may be powered by a standard AC/DCconverter. The radio of GS box 700 may be identical to the radio used onthe space vehicle. Standard RF coaxial connectors may be provided forthe transmit and receive signal paths, enabling ground station setupwithout requiring tools.

FIG. 8 is a photograph illustrating a prototype GS box 800, according toan embodiment of the present invention. GS box 800 has a rugged casethat houses sensitive internal electronics. GS box 800 enables controlof antenna orientation and facilitates communication with space vehiclesvia the antenna.

FIG. 9 is a photograph illustrating a prototype ground station antennaassembly 900, according to an embodiment of the present invention. Inantenna assembly 900, separate antennas are used for transmission andreception, and antenna pairs are used for each to enable circularpolarization. As can be seen, antenna assembly 900 is relativelycompact, enabling deployment in a large variety of operatingenvironments. The RF box is visible next to the antenna.

An advantage of some embodiments is that they can be built using COTSparts, including the rotor, antennas, ground station box boards,controlling computer, etc. The system may only cost a few thousanddollars in some embodiments. The system may also be deployable innon-pristine environments. In a poor conditions test in a snowyenvironment, the prototype system performed normally.

FIG. 10 is a perspective view illustrating the inside of a groundstation/field unit (GS/FU) box 1000, according to an embodiment of thepresent invention. GS/FU box 1000 includes an analog radio board 1010that sends and receives radio signals via an antenna (not shown). Adigital radio board 1020 interfaces with analog radio board 1010 andprovides digital radio functionality. GS/FU box 1000 achieves higherdata rates than other satellite communication systems relative to thesize and power consumption. A microcontroller board 1030, such as aLinux™ single board computer (SBC), e.g., Beagleboard™, providesprocessing for GS/FU box 1000. A backplane 1040 connects the boards,facilitating communication therebetween, and also connects to a powersupply (not shown). In some embodiments, the dimensions areapproximately 4×4×2 inches. In certain embodiments, all functionalitymay be achieved with, and performed by, a single board.

Some embodiments may have various ports, such as universal serial bus(USB), Ethernet, power ports, an external antenna connector, etc. Incertain embodiments, the ports of GS/FU box 1000 may be exposed. In suchembodiments, a protective enclosure that shields GS/FU box 1000 from theelements should be used. The protective enclosure may include a casingprotecting GS/FU box 1000 from weather, vents, cooling fans, etc.

FIG. 11 is a perspective view illustrating a GS/FU box 1100, accordingto an embodiment of the present invention. GS/FU box 1100 includes aCATS port 1110, a USB port 1120, a general purpose input/output (GPIO)port 1130, and an N-connector port 1140 for receiving a radio frequency(RF) signal. A light emitting diode (LED) power indicator 1150 indicateswhether GS/FU box 1100 is on and has power.

Per the above, a common box may be used for deployment in a groundstation or a field unit in some embodiments. In certain embodiments, thelogic enabling ground station functionality, field unit functionality,or both may be stored on a storage device, such as a secure digital (SD)card, a flash drive, or any other storage device that may be pluggedinto the GS/FU box, which may then read and executes the code. In someembodiments, code containing the logic may be downloaded by the GS/FUbox via a wired or wireless connection. Encryption keys may also bestored on the storage device or downloaded from a remote computingsystem. This may enable certain security privileges on a per-user basis(e.g., administrator, user, etc.).

FIG. 12 is an architectural diagram illustrating a field unit system1200, according to an embodiment of the present invention. A directcurrent (DC) power supply 1210 provides power to a field unit box 1220.In some embodiments, alternating current (AC) power may be used insteadof DC power. Field unit box 1220 communicates with one or more spacevehicles via an antenna 1230. In some embodiments, field unit 1220 mayonly receive data from space vehicles and may not transmit data, or maylack transmission capabilities. A sensor 1240 is connected to field unitbox 1220. In this embodiment, field unit box 1220 serves as a modem torelay data taken by sensor 1240 back to a ground station, or to allowthe ground station to command sensor 1240.

In some embodiments, deployment of field unit system 1200 may berelatively easy and not require special expertise. For instance, in someembodiments, a user may plug sensor 1240 into field unit box 1220, plugantenna 1230 into field unit box 1220, position antenna 1230, plug DCpower supply 1210 into field unit box 1220, and walk away. This ease ofdeployment is not possible with conventional field unit systems.

FIG. 13 is a perspective view illustrating a field unit box 1300,according to an embodiment of the present invention. Field unit box 1300includes a patch antenna 1310 that enables field unit 1300 to uplinkdata from external sources, such as data detected by sensors attached toRJ45 Ethernet interface 1320, to a space vehicle. Communications may useany desired authentication and encryption format, such as NSA Suite B.Field unit 1300 also includes a USB interface 1330, an RGB LED 1340 thatindicates field unit status, and a power jack 1350, which may have awide power supply range. Field unit 1300 may share at least some commonhardware and software with a space vehicle and ground station in someembodiments.

FIGS. 14A-C illustrate a closed and opened prototype field unit box 1400and boards 1410 stacked within field unit box 1400, according to anembodiment of the present invention. Field unit box 1400 is compact andeasily accessible once the case is opened.

Software

In some embodiments, orbit tracking software may provide tracking, rotorcontrol, Doppler calculation, etc. A script may be provided forautomatic two-line element (TLE) updates. The user interface may berelatively simple, with a graphical representation of space vehiclelocations and ranges on a map. The user interface may also displaysatellite communications and provide logging. Conventional groundstation software is complex and requires extensively trained,specialized users to operate. Moreover, conventional ground stationstypically require an operator to be present, i.e., they do not supportunattended operations. By contrast, some embodiments present a simpleuser interface, enabling non-expert users to task and operate thesatellite quickly, and enable fully automated “lights-out” space vehicleoperations, vastly lowering the cost and infrastructure required tooperate the space vehicle system.

FIG. 15 is a screenshot 1300 illustrating ground station controlsoftware, according to an embodiment of the present invention. Theground station control software includes a map 1510 that displayssatellite positions relative to the Earth and ground footprints. Asatellite selection panel 1520 allows a user to view data for varioussatellites, such as azimuth, elevation, range, height, etc. Selectionpanel 1520 also allows the user to select a satellite to control.

An azumith/elevation panel 1530 shows the azimuth and elevation for theselected satellite. A radio control panel 1540 shows the frequency atthe satellite, Doppler shift, and transmit frequency for uplink anddownlink. The uplink transmit frequency and downlink frequency at thesatellite can also be controlled. A command interface 1550 allows theuser to enter commands and also shows log data. In certain embodiments,all of the panels may be integrated into a single window. The controlsoftware may allow full control over the satellite and provide a largeamount of diagnostic information. Simplified ground station software isillustrated in screenshot 1600 of FIG. 16.

Per the above, the field unit may not provide the user with the abilityto control space vehicles or to communicate with space vehicles at all.The field unit may steam data to a computing system associated with thefield unit and display the data in a graphical user interface (GUI). Forexample, the field unit software may enable the user to get certain datatransmitted by the space vehicle, such as photos, video, audio, etc.

FIG. 17 is a block diagram 1700 illustrating connection setup for aground station, space vehicle, and field unit system, according to anembodiment of the present invention. In this embodiment, ground station1710 initiates a connection with space vehicle 1720. Space vehicle 1720then initiates a connection with field unit 1730. Field unit 1730 cannotinitiate connections in this embodiment. Proof of identity, keyexchange, data encryption, and other security may be performed usingknown techniques (e.g., digital signature algorithm (DSA),station-to-station (STS) protocol, etc.).

Conventional space vehicle systems use FAT file systems or similarformats, using Internet Protocol (IP) or similar protocols for filetransfer. In these systems, files are stored sequentially, and aresimilarly transferred sequentially. Specifically, for file transfer, thefile is split into a set of datagrams that are assigned a sequencenumber and again transferred sequentially, using a retry protocol tore-send corrupted datagrams. This type of transfer protocol assumes asingle sender and receiver (destination). A major disadvantage of thistype of system is that it does not allow for files to be transmittedpiecemeal, using multiple satellites to transfer different portions ofthe file.

To address this and other issues, some embodiments combine a number ofdifferent features of various file systems and transfer protocols tocreate a new, unique approach. Files may be split into datagrams asbefore, but a metadata header may be attached that contains the originof the file, the file name, the sequence number, and other informationto enable data transfer. These datagrams may be wholly self-contained,and may be transferred and stored individually on an ad-hoc basis. Thesender may track which datagrams were successfully transferred, using anack/retry protocol, without knowledge of the final destination.Intermediate nodes may then be used to store and eventually re-transmitthis data as many times as needed until the data is finally gatheredtogether and reassembled at the destination. The resulting system is acombination of a distributed file system and a transfer protocol that isuniquely suited to constellations of small satellites.

An advantage of this approach is that files can be transferred out oforder and reassembled. Also, multiple space vehicles may transmit orreceive different portions of a file. For instance, a first spacevehicle may get a frame of an uplink file. Later, a second satellite mayget several more frames, etc. This also works in the reverse directionwith respect to the GS/FU. A satellite may transfer some fraction offrames to the first ground station it encounters, transfer more data toa second ground station, and so on. The file may become more and morefractionated, but all data is still present to eventually re-assemblethe file at a final receiving node, without the ultimate sending andreceiving nodes ever directly communicating with one another.

It will be readily understood that the components of various embodimentsof the present invention, as generally described and illustrated in thefigures herein, may be arranged and designed in a wide variety ofdifferent configurations. Thus, the detailed description of theembodiments of the present invention, as represented in the attachedfigures, is not intended to limit the scope of the invention as claimed,but is merely representative of selected embodiments of the invention.

The features, structures, or characteristics of the invention describedthroughout this specification may be combined in any suitable manner inone or more embodiments. For example, reference throughout thisspecification to “certain embodiments,” “some embodiments,” or similarlanguage means that a particular feature, structure, or characteristicdescribed in connection with the embodiment is included in at least oneembodiment of the present invention. Thus, appearances of the phrases“in certain embodiments,” “in some embodiment,” “in other embodiments,”or similar language throughout this specification do not necessarily allrefer to the same group of embodiments and the described features,structures, or characteristics may be combined in any suitable manner inone or more embodiments.

It should be noted that reference throughout this specification tofeatures, advantages, or similar language does not imply that all of thefeatures and advantages that may be realized with the present inventionshould be or are in any single embodiment of the invention. Rather,language referring to the features and advantages is understood to meanthat a specific feature, advantage, or characteristic described inconnection with an embodiment is included in at least one embodiment ofthe present invention. Thus, discussion of the features and advantages,and similar language, throughout this specification may, but do notnecessarily, refer to the same embodiment.

Furthermore, the described features, advantages, and characteristics ofthe invention may be combined in any suitable manner in one or moreembodiments. One skilled in the relevant art will recognize that theinvention can be practiced without one or more of the specific featuresor advantages of a particular embodiment. In other instances, additionalfeatures and advantages may be recognized in certain embodiments thatmay not be present in all embodiments of the invention.

One having ordinary skill in the art will readily understand that theinvention as discussed above may be practiced with steps in a differentorder, and/or with hardware elements in configurations which aredifferent than those which are disclosed. Therefore, although theinvention has been described based upon these preferred embodiments, itwould be apparent to those of skill in the art that certainmodifications, variations, and alternative constructions would beapparent, while remaining within the spirit and scope of the invention.In order to determine the metes and bounds of the invention, therefore,reference should be made to the appended claims.

1. An apparatus, comprising: at least one hardware board configured toenable operation of the apparatus as a field unit and a ground station,wherein software controls whether the apparatus operates as a field unitor a ground station without physical modification to the at least onehardware board.
 2. The apparatus of claim 1, wherein the at least onehardware board comprises commercial off-the-shelf (COTS) parts.
 3. Theapparatus of claim 1, wherein the at least one hardware board comprises:an analog radio board configured to send and receive radio signals viaan antenna; a digital radio board configured to interface with theanalog radio board and provide digital radio functionality; amicrocontroller board configured to provide processing for theapparatus; and a backplane that connects the analog radio board, digitalradio board, and microcontroller board, facilitating communicationbetween the boards.
 4. The apparatus of claim 1, wherein dimensions ofthe apparatus are approximately four inches by four inches by two inches(4×4×2).
 5. The apparatus of claim 1, further comprising: a universalserial bus (USB) port, an Ethernet port, a power port, an externalantenna connector, or any combination thereof.
 6. The apparatus of claim1, further comprising: a protective enclosure configured to provideprotection from weather.
 7. The apparatus of claim 1, furthercomprising: a CATS port, a universal serial bus (USB) port, a generalpurpose input/output (GPIO) port, and an N-connector port configured toreceive a radio frequency (RF) signal.
 8. The apparatus of claim 1,wherein the software controlling whether the apparatus operates as afield unit or a ground station is stored on an external storage devicethat can be plugged into the apparatus, which then reads and executesthe stored software.
 9. The apparatus of claim 1, further comprising:hardware configured to enable wired or wireless communication, whereinthe hardware downloads the software to enable operation of the apparatusas a field unit or a ground station.
 10. The apparatus of claim 1,wherein encryption keys enabling security privileges on a per-user basisare stored on the apparatus and used by the software.
 11. The apparatusof claim 1, wherein the apparatus is configured to be controlled by alocal or remote external computer.
 12. The apparatus of claim 1, whereinthe apparatus is configured to control orientation of an antenna via arotor control box, and to send data to and receive data from a spacevehicle via a transceiver box.
 13. The apparatus of claim 1, wherein theapparatus is attached to an antenna or integrated with a rotor of theantenna.
 14. A field unit/ground station (FU/GS) box, comprising: ananalog radio board configured to send and receive radio signals via anantenna; a digital radio board configured to interface with the analogradio board and provide digital radio functionality; a microcontrollerboard configured to provide processing for the FU/GS box; and abackplane that connects the analog radio board, digital radio board, andmicrocontroller board, facilitating communication between the boards,wherein software controls whether the FU/GS box operates as a field unitor a ground station without physical modification to the boards.
 15. TheFU/GS box of claim 14, further comprising: a protective enclosureconfigured to provide protection from weather.
 16. The FU/GS box ofclaim 14, wherein the software controlling whether the FU/GS boxoperates as a field unit or a ground station is stored on an externalstorage device that can be plugged into the FU/GS box, which then readsand executes the stored software.
 17. The FU/GS box of claim 14, furthercomprising: hardware configured to enable wired or wirelesscommunication, wherein the hardware downloads the software to enableoperation of the FU/GS box as a field unit or a ground station.
 18. Asystem, comprising: at least one field unit; and at least one groundstation, wherein the at least one field unit and the at least one groundstation have common hardware.
 19. The system of claim 18, whereinsoftware controls whether the at least one field unit and the at leastone ground station operate as a field unit or a ground station.
 20. Thesystem of claim 18, wherein each of the at least one field unit and theat least one ground station comprises: an analog radio board configuredto send and receive radio signals via an antenna; a digital radio boardconfigured to interface with the analog radio board and provide digitalradio functionality; a microcontroller board configured to provideprocessing for the field unit or ground station; and a backplane thatconnects the analog radio board, digital radio board, andmicrocontroller board, facilitating communication between the boards.